Skip to main content

Diagnostics & Setup app

The driver ships a browser Diagnostics & Setup app, hosted on the processor. It is the fastest way to confirm the 2N is set up correctly and to see what the driver is seeing — without a processor console.

Open it from the driver's configuration: the Diagnostics & Setup field carries its URL. The app is served from the processor, so it works on site with no outbound internet, and it is reachable whether or not the driver is licensed.

The app has two tabs: Diagnostics and Troubleshooter.

Diagnostics​

A live view of the driver's state, plus the tools to exercise the 2N:

  • Status — the connection to the 2N, the current switch, input, output and call state, the last device event, and the licence status. This is the "is it working, right now" view.
  • Event log — the recent device events from the 2N, newest first (switch changes, input open/close, motion, noise, call button and call state). The quickest way to confirm a physical action on the 2N (a contact closing, a button press) is reaching the driver.
  • Test actions — fire real actions on the 2N to prove the wiring end to end during commissioning: Test On / Test Off for each switch, and Place a test SIP call from the doorstation, then hang it up.
Test actions fire on the real device

The test actions drive the actual 2N (they are the same calls the tile makes), so use them on site knowing the strike will actually release or the panels will actually ring.

Troubleshooter​

Runs an ordered set of connection checks against the live 2N and reports a verdict, plain-language detail and a fix for anything wrong. The checks run in order, and each depends on the one before — if a check fails, the ones that depend on it are skipped with the reason, so you fix the real cause rather than chasing every red row:

  1. Network reachability — is the 2N reachable at its address?
  2. 2N HTTP API enabled — is the HTTP API answering?
  3. API credentials — does the 2N accept the configured username and password?
  4. API services & privileges — is the account granted the System, Switch and Event log (Logging) services? (Also warns if the 2N's Enhanced Integration / Automation licence is not active.)
  5. Switches (strikes / relays) — is at least one switch enabled, and how is each configured?
  6. Digital inputs — are inputs available to monitor?
  7. SIP call control — is a SIP account registered? (A warning, not a failure — switches and inputs work without SIP.)

The troubleshooter produces a copyable text report you can paste into a support ticket.